Synchronize collaboration entity files

ABSTRACT

A database system is arranged to support collaboration among users of a file in a feed system of a multi-user social network database driven system, wherein at least some of the users are permitted to upload a file to the feed from a remote computing device, and other users may have permission to collaborate on modifying the file. A sync client application executable on a remote user machine enables an authorize user to select “sync all files in the feed,” which triggers (a) download of the latest version of all files in the feed from the cloud to all users associated with the feed, and (b) subsequent automatic synchronization of the files by selectively uploading to the cloud database a modified local copy of the file from a user machine, and then downloading a latest version of the modified file to all of the users associated with the feed.

COPYRIGHT NOTICE

Copyright 2015 Salesforce.com, Inc. A portion of the disclosure of thispatent document contains material which is subject to copyrightprotection. The copyright owner has no objection to the facsimilereproduction by anyone of the patent document or the patent disclosure,as it appears in the United States Patent and Trademark Office patentfile or records, but otherwise reserves all copyright rights whatsoever.

TECHNICAL FIELD

One or more implementations relate generally to collaboration inauthoring, posting and using electronic items in a network coupled to adatabase system or service.

BACKGROUND

“Cloud computing” services provide shared resources, software, andinformation to computers and other devices upon request or on demand.Cloud computing typically involves the over-the-Internet provision ofdynamically-scalable and often virtualized resources. Technical detailscan be abstracted from end-users, who no longer have need for expertisein, or control over, the technology infrastructure “in the cloud” thatsupports them. In cloud computing environments, software applicationscan be accessible over the Internet rather than installed locally onpersonal or in-house computer systems. Some of the applications oron-demand services provided to end-users can include the ability for auser to create, view, modify, store and share documents and other files.

BRIEF DESCRIPTION OF THE DRAWINGS

The included drawings are for illustrative purposes and serve to provideexamples of possible structures and operations for the disclosedinventive systems, apparatus, methods and computer-readable storagemedia. These drawings in no way limit any changes in form and detailthat may be made by one skilled in the art without departing from thespirit and scope of the disclosed implementations.

FIG. 1A shows a block diagram of an example environment in which anon-demand database service can be used according to someimplementations.

FIG. 1B shows a block diagram of example implementations of elements ofFIG. 1A and example interconnections between these elements according tosome implementations.

FIG. 2A shows a system diagram of example architectural components of anon-demand database service environment according to someimplementations.

FIG. 2B shows a system diagram further illustrating examplearchitectural components of an on-demand database service environmentaccording to some implementations.

FIG. 3 shows an example of a group feed display on a group profile pageaccording to some implementations.

FIG. 4 shows an example of a record feed display on a record profilepage according to some implementations.

FIG. 5 shows an example of a feed screen display for a private group ofusers with a popup control interface.

FIG. 6 shows an example of a local file system directory in whichselected files may be automatically collected and maintained insynchrony.

FIG. 7 is a simplified block diagram illustrating an example of a systemarchitecture that employs a client application program in support ofsynchronization of database files for collaboration.

FIG. 8 is a simplified block diagram showing the principle components ofone example of a synchronization client application program.

FIG. 9 is an illustration of an example of a user interface componentfor a synchronization client application program.

FIG. 10 illustrates a display of a file system folder of filesassociated with synchronization client application program forsynchronization.

FIG. 11 illustrates an example of a sync status panel that may bedisplayed in a user interface of a synchronization client applicationprogram.

DETAILED DESCRIPTION

Examples of systems, apparatus, computer-readable storage media, andmethods according to the disclosed implementations are described in thissection. These examples are being provided solely to add context and aidin the understanding of the disclosed implementations. It will thus beapparent to one skilled in the art that the disclosed implementationsmay be practiced without some or all of the specific details provided.In other instances, certain process or method operations, also referredto herein as “blocks,” have not been described in detail in order toavoid unnecessarily obscuring the disclosed implementations. Otherimplementations and applications also are possible, and as such, thefollowing examples should not be taken as definitive or limiting eitherin scope or setting.

In the following detailed description, references are made to theaccompanying drawings, which form a part of the description and in whichare shown, by way of illustration, specific implementations. Althoughthese disclosed implementations are described in sufficient detail toenable one skilled in the art to practice the implementations, it is tobe understood that these examples are not limiting, such that otherimplementations may be used and changes may be made to the disclosedimplementations without departing from their spirit and scope. Forexample, the blocks of the methods shown and described herein are notnecessarily performed in the order indicated in some otherimplementations. Additionally, in some other implementations, thedisclosed methods may include more or fewer blocks than are described.As another example, some blocks described herein as separate blocks maybe combined in some other implementations. Conversely, what may bedescribed herein as a single block may be implemented in multiple blocksin some other implementations. Additionally, the conjunction “or” isintended herein in the inclusive sense where appropriate unlessotherwise indicated; that is, the phrase “A, B or C” is intended toinclude the possibilities of “A,” “B,” “C,” “A and B,” “B and C,” “A andC” and “A, B and C.”

Some implementations described and referenced herein are directed tosystems, apparatus, computer-implemented methods and computer-readablestorage media, or a combination thereof, arranged to supportcollaboration in the creation, editing and sharing electronic items inan enterprise social networking system.

In some embodiments, each of the members of a group of users who wouldcollaborate on a file may install an instance of a synchronizationclient application program on their machine, or on each one of theirmultiple machines if they choose to do so. One example of such a groupis the group associated to the feed display example of FIG. 5. With asingle instruction or “click” by the group admin (or other dulyauthorized user), all of the files in the feed will be synchronized toall of the members of the group who run such a sync client. Any and allchanges made by an authorized collaborator thereafter will beautomatically distributed to the local file systems on each of thoseuser machines that have the sync client. Further, any new file added tothe same feed will be automatically distributed to all members of thefeed who have the sync client app.

In some implementations, the users described herein are users (or“members”) of an interactive online “enterprise social network,” alsoreferred to herein as an “enterprise social networking system,” an“enterprise collaborative network,” or more simply as an “enterprisenetwork.” Such online enterprise networks are increasingly becoming acommon way to facilitate communication among people, any of whom can berecognized as enterprise users. One example of an online enterprisesocial network is Chatter®, provided by salesforce.com, inc. of SanFrancisco, Calif. salesforce.com, inc. is a provider of enterprisesocial networking services, customer relationship management (CRM)services and other database management services, any of which can beaccessed and used in conjunction with the techniques disclosed herein insome implementations. These various services can be provided in a cloudcomputing environment as described herein, for example, in the contextof a multi-tenant database system. Some of the described techniques orprocesses can be implemented without having to install software locally,that is, on computing devices of users interacting with servicesavailable through the cloud. While the disclosed implementations may bedescribed with reference to Chatter® and more generally to enterprisesocial networking, those of ordinary skill in the art should understandthat the disclosed techniques are neither limited to Chatter® nor to anyother services and systems provided by Salesforce.com, Inc. and can beimplemented in the context of various other database systems such ascloud-based systems that are not part of a multi-tenant database systemor which do not provide enterprise social networking services.

I. Example System Overview

FIG. 1A shows a block diagram of an example of an environment 10 inwhich an on-demand database service can be used in accordance with someimplementations. The environment 10 includes user systems 12, a network14, a database system 16 (also referred to herein as a “cloud-basedsystem”), a processor system 17, an application platform 18, a networkinterface 20, tenant database 22 for storing tenant data 23, systemdatabase 24 for storing system data 25, program code 26 for implementingvarious functions of the system 16, and process space 28 for executingdatabase system processes and tenant-specific processes, such as runningapplications as part of an application hosting service. In some otherimplementations, environment 10 may not have all of these components orsystems, or may have other components or systems instead of, or inaddition to, those listed above.

In some implementations, the environment 10 is an environment in whichan on-demand database service exists. An on-demand database service,such as that which can be implemented using the system 16, is a servicethat is made available to users outside of the enterprise(s) that own,maintain or provide access to the system 16. As described above, suchusers generally do not need to be concerned with building or maintainingthe system 16. Instead, resources provided by the system 16 may beavailable for such users' use when the users need services provided bythe system 16; that is, on the demand of the users. Some on-demanddatabase services can store information from one or more tenants intotables of a common database image to form a multi-tenant database system(MTS). The term “multi-tenant database system” can refer to thosesystems in which various elements of hardware and software of a databasesystem may be shared by one or more customers or tenants. For example, agiven application server may simultaneously process requests for a greatnumber of customers, and a given database table may store rows of datasuch as feed items for a potentially much greater number of customers. Adatabase image can include one or more database objects. A relationaldatabase management system (RDBMS) or the equivalent can execute storageand retrieval of information against the database object(s).

Application platform 18 can be a framework that allows the applicationsof system 16 to execute, such as the hardware or software infrastructureof the system 16. In some implementations, the application platform 18enables the creation, management and execution of one or moreapplications developed by the provider of the on-demand databaseservice, users accessing the on-demand database service via user systems12, or third party application developers accessing the on-demanddatabase service via user systems 12.

In some implementations, the system 16 implements a web-based customerrelationship management (CRM) system. For example, in some suchimplementations, the system 16 includes application servers configuredto implement and execute CRM software applications as well as providerelated data, code, forms, renderable web pages and documents and otherinformation to and from user systems 12 and to store to, and retrievefrom, a database system related data, objects, and Web page content. Insome MTS implementations, data for multiple tenants may be stored in thesame physical database object in tenant database 22. In some suchimplementations, tenant data is arranged in the storage medium(s) oftenant database 22 so that data of one tenant is kept logically separatefrom that of other tenants so that one tenant does not have access toanother tenant's data, unless such data is expressly shared. The system16 also implements applications other than, or in addition to, a CRMapplication. For example, the system 16 can provide tenant access tomultiple hosted (standard and custom) applications, including a CRMapplication. User (or third party developer) applications, which may ormay not include CRM, may be supported by the application platform 18.The application platform 18 manages the creation and storage of theapplications into one or more database objects and the execution of theapplications in one or more virtual machines in the process space of thesystem 16.

According to some implementations, each system 16 is configured toprovide web pages, forms, applications, data and media content to user(client) systems 12 to support the access by user systems 12 as tenantsof system 16. As such, system 16 provides security mechanisms to keepeach tenant's data separate unless the data is shared. If more than oneMTS is used, they may be located in close proximity to one another (forexample, in a server farm located in a single building or campus), orthey may be distributed at locations remote from one another (forexample, one or more servers located in city A and one or more serverslocated in city B). As used herein, each MTS could include one or morelogically or physically connected servers distributed locally or acrossone or more geographic locations. Additionally, the term “server” ismeant to refer to a computing device or system, including processinghardware and process space(s), an associated storage medium such as amemory device or database, and, in some instances, a databaseapplication (for example, OODBMS or RDBMS) as is well known in the art.It should also be understood that “server system” and “server” are oftenused interchangeably herein. Similarly, the database objects describedherein can be implemented as part of a single database, a distributeddatabase, a collection of distributed databases, a database withredundant online or offline backups or other redundancies, etc., and caninclude a distributed database or storage network and associatedprocessing intelligence.

The network 14 can be or include any network or combination of networksof systems or devices that communicate with one another. For example,the network 14 can be or include any one or any combination of a LAN(local area network), WAN (wide area network), telephone network,wireless network, cellular network, point-to-point network, starnetwork, token ring network, hub network, or other appropriateconfiguration. The network 14 can include a TCP/IP (Transfer ControlProtocol and Internet Protocol) network, such as the global internetworkof networks often referred to as the “Internet” (with a capital “I”).The Internet will be used in many of the examples herein. However, itshould be understood that the networks that the disclosedimplementations can use are not so limited, although TCP/IP is afrequently implemented protocol.

The user systems 12 can communicate with system 16 using TCP/IP and, ata higher network level, other common Internet protocols to communicate,such as HTTP, FTP, AFS, WAP, etc. In an example where HTTP is used, eachuser system 12 can include an HTTP client commonly referred to as a “webbrowser” or simply a “browser” for sending and receiving HTTP signals toand from an HTTP server of the system 16. Such an HTTP server can beimplemented as the sole network interface 20 between the system 16 andthe network 14, but other techniques can be used in addition to orinstead of these techniques. In some implementations, the networkinterface 20 between the system 16 and the network 14 includes loadsharing functionality, such as round-robin HTTP request distributors tobalance loads and distribute incoming HTTP requests evenly over a numberof servers. In MTS implementations, each of the servers can have accessto the MTS data; however, other alternative configurations may be usedinstead.

The user systems 12 can be implemented as any computing device(s) orother data processing apparatus or systems usable by users to access thedatabase system 16. For example, any of user systems 12 can be a desktopcomputer, a work station, a laptop computer, a tablet computer, ahandheld computing device, a mobile cellular phone (for example, a“smartphone”), or any other Wi-Fi-enabled device, wireless accessprotocol (WAP)-enabled device, or other computing device capable ofinterfacing directly or indirectly to the Internet or other network. Theterms “user system” and “computing device” are used interchangeablyherein with one another and with the term “computer.” As describedabove, each user system 12 typically executes an HTTP client, forexample, a web browsing (or simply “browsing”) program, such as a webbrowser based on the WebKit platform, Microsoft's Internet Explorerbrowser, Netscape's Navigator browser, Opera's browser, Mozilla'sFirefox browser, or a WAP-enabled browser in the case of a cellularphone, PDA or other wireless device, or the like, allowing a user (forexample, a subscriber of on-demand services provided by the system 16)of the user system 12 to access, process and view information, pages andapplications available to it from the system 16 over the network 14.

Each user system 12 also typically includes one or more user inputdevices, such as a keyboard, a mouse, a trackball, a touch pad, a touchscreen, a pen or stylus or the like, for interacting with a graphicaluser interface (GUI) provided by the browser on a display (for example,a monitor screen, liquid crystal display (LCD), light-emitting diode(LED) display, among other possibilities) of the user system 12 inconjunction with pages, forms, applications and other informationprovided by the system 16 or other systems or servers. For example, theuser interface device can be used to access data and applications hostedby system 16, and to perform searches on stored data, and otherwiseallow a user to interact with various GUI pages that may be presented toa user. As discussed above, implementations are suitable for use withthe Internet, although other networks can be used instead of or inaddition to the Internet, such as an intranet, an extranet, a virtualprivate network (VPN), a non-TCP/IP based network, any LAN or WAN or thelike.

The users of user systems 12 may differ in their respective capacities,and the capacity of a particular user system 12 can be entirelydetermined by permissions (permission levels) for the current user ofsuch user system. For example, where a salesperson is using a particularuser system 12 to interact with the system 16, that user system can havethe capacities allotted to the salesperson. However, while anadministrator is using that user system 12 to interact with the system16, that user system can have the capacities allotted to thatadministrator. Where a hierarchical role model is used, users at onepermission level can have access to applications, data, and databaseinformation accessible by a lower permission level user, but may nothave access to certain applications, database information, and dataaccessible by a user at a higher permission level. Thus, different usersgenerally will have different capabilities with regard to accessing andmodifying application and database information, depending on the users'respective security or permission levels (also referred to as“authorizations”).

According to some implementations, each user system 12 and some or allof its components are operator-configurable using applications, such asa browser, including computer code executed using a central processingunit (CPU) such as an Intel Pentium® processor or the like. Similarly,the system 16 (and additional instances of an MTS, where more than oneis present) and all of its components can be operator-configurable usingapplication(s) including computer code to run using the processor system17, which may be implemented to include a CPU, which may include anIntel Pentium® processor or the like, or multiple CPUs.

The system 16 includes tangible computer-readable media havingnon-transitory instructions stored thereon/in that are executable by orused to program a server or other computing system (or collection ofsuch servers or computing systems) to perform some of the implementationof processes described herein. For example, computer program code 26 canimplement instructions for operating and configuring the system 16 tointercommunicate and to process web pages, applications and other dataand media content as described herein. In some implementations, thecomputer code 26 can be downloadable and stored on a hard disk, but theentire program code, or portions thereof, also can be stored in anyother volatile or non-volatile memory medium or device as is well known,such as a ROM or RAM, or provided on any media capable of storingprogram code, such as any type of rotating media including floppy disks,optical discs, digital versatile disks (DVD), compact disks (CD),microdrives, and magneto-optical disks, and magnetic or optical cards,nanosystems (including molecular memory ICs), or any other type ofcomputer-readable medium or device suitable for storing instructions ordata. Additionally, the entire program code, or portions thereof, may betransmitted and downloaded from a software source over a transmissionmedium, for example, over the Internet, or from another server, as iswell known, or transmitted over any other existing network connection asis well known (for example, extranet, VPN, LAN, etc.) using anycommunication medium and protocols (for example, TCP/IP, HTTP, HTTPS,Ethernet, etc.) as are well known. It will also be appreciated thatcomputer code for the disclosed implementations can be realized in anyprogramming language that can be executed on a server or other computingsystem such as, for example, C, C++, HTML, any other markup language,Java™, JavaScript, ActiveX, any other scripting language, such as VBScript, and many other programming languages as are well known may beused. (Java™ is a trademark of Sun Microsystems, Inc.).

FIG. 1B shows a block diagram of example implementations of elements ofFIG. 1A and example interconnections between these elements according tosome implementations. That is, FIG. 1B also illustrates environment 10,but FIG. 1B, various elements of the system 16 and variousinterconnections between such elements are shown with more specificityaccording to some more specific implementations. Additionally, in FIG.1B, the user system 12 includes a processor system 12A, a memory system12B, an input system 12C, and an output system 12D. The processor system12A can include any suitable combination of one or more processors. Thememory system 12B can include any suitable combination of one or morememory devices. The input system 12C can include any suitablecombination of input devices, such as one or more touchscreeninterfaces, keyboards, mice, trackballs, scanners, cameras, orinterfaces to networks. The output system 12D can include any suitablecombination of output devices, such as one or more display devices,printers, or interfaces to networks.

In FIG. 1B, the network interface 20 is implemented as a set ofapplication servers 100 ₁-100 _(N). Each application server 100, alsoreferred to herein as an “app server”, is configured to communicate withtenant database 22 and the tenant data 23 therein, as well as systemdatabase 24 and the system data 25 therein, to serve requests receivedfrom the user systems 12. The tenant data 23 can be divided intoindividual tenant storage spaces 112, which can be physically orlogically arranged or divided. Within each tenant storage space 112,user storage 114 and application metadata 116 can similarly be allocatedfor each user. For example, a copy of a user's most recently used (MRU)items can be stored to user storage 114. Similarly, a copy of MRU itemsfor an entire organization that is a tenant can be stored to tenantstorage space 112.

The process space 28 includes system process space 102, individualtenant process spaces 104 and a tenant management process space 110. Theapplication platform 18 includes an application setup mechanism 38 thatsupports application developers' creation and management ofapplications. Such applications and others can be saved as metadata intotenant database 22 by save routines 36 for execution by subscribers asone or more tenant process spaces 104 managed by tenant managementprocess 110, for example. Invocations to such applications can be codedusing PL/SOQL 34, which provides a programming language style interfaceextension to API 32. A detailed description of some PL/SOQL languageimplementations is discussed in commonly assigned U.S. Pat. No.7,730,478, titled METHOD AND SYSTEM FOR ALLOWING ACCESS TO DEVELOPEDAPPLICATIONS VIA A MULTI-TENANT ON-DEMAND DATABASE SERVICE, by CraigWeissman, issued on Jun. 1, 2010, and hereby incorporated by referencein its entirety and for all purposes. Invocations to applications can bedetected by one or more system processes, which manage retrievingapplication metadata 116 for the subscriber making the invocation andexecuting the metadata as an application in a virtual machine.

The system 16 of FIG. 1B also includes a user interface (UI) 30 and anapplication programming interface (API) 32 to system 16 residentprocesses to users or developers at user systems 12. In some otherimplementations, the environment 10 may not have the same elements asthose listed above or may have other elements instead of, or in additionto, those listed above.

Each application server 100 can be communicably coupled with tenantdatabase 22 and system database 24, for example, having access to tenantdata 23 and system data 25, respectively, via a different networkconnection. For example, one application server 100 ₁ can be coupled viathe network 14 (for example, the Internet), another application server100 _(N-1) can be coupled via a direct network link, and anotherapplication server 100 _(N) can be coupled by yet a different networkconnection. Transfer Control Protocol and Internet Protocol (TCP/IP) areexamples of typical protocols that can be used for communicating betweenapplication servers 100 and the system 16. However, it will be apparentto one skilled in the art that other transport protocols can be used tooptimize the system 16 depending on the network interconnections used.

In some implementations, each application server 100 is configured tohandle requests for any user associated with any organization that is atenant of the system 16. Because it can be desirable to be able to addand remove application servers 100 from the server pool at any time andfor various reasons, in some implementations there is no server affinityfor a user or organization to a specific application server 100. In somesuch implementations, an interface system implementing a load balancingfunction (for example, an F5 Big-IP load balancer) is communicablycoupled between the application servers 100 and the user systems 12 todistribute requests to the application servers 100. In oneimplementation, the load balancer uses a least-connections algorithm toroute user requests to the application servers 100. Other examples ofload balancing algorithms, such as round robin andobserved-response-time, also can be used. For example, in someinstances, three consecutive requests from the same user could hit threedifferent application servers 100, and three requests from differentusers could hit the same application server 100. In this manner, by wayof example, system 16 can be a multi-tenant system in which system 16handles storage of, and access to, different objects, data andapplications across disparate users and organizations.

In one example storage use case, one tenant can be a company thatemploys a sales force where each salesperson uses system 16 to manageaspects of their sales. A user can maintain contact data, leads data,customer follow-up data, performance data, goals and progress data,etc., all applicable to that user's personal sales process (for example,in tenant database 22). In an example of a MTS arrangement, because allof the data and the applications to access, view, modify, report,transmit, calculate, etc., can be maintained and accessed by a usersystem 12 having little more than network access, the user can managehis or her sales efforts and cycles from any of many different usersystems at virtually any location. For example, when a salesperson isvisiting a customer and the customer has Internet access in their lobby,the salesperson can obtain critical updates regarding that customerwhile waiting for the customer to arrive in the lobby.

While each user's data can be stored separately from other users' dataregardless of the employers of each user, some data can beorganization-wide data shared or accessible by several users or all ofthe users for a given organization that is a tenant. Thus, there can besome data structures managed by system 16 that are allocated at thetenant level while other data structures can be managed at the userlevel. Because an MTS can support multiple tenants including possiblecompetitors, the MTS can have security protocols that keep data,applications, and application use separate. Also, because many tenantsmay opt for access to an MTS rather than maintain their own system,redundancy, up-time, and backup are additional functions that can beimplemented in the MTS. In addition to user-specific data andtenant-specific data, the system 16 also can maintain system level datausable by multiple tenants or other data. Such system level data caninclude industry reports, news, postings, and the like that are sharableamong tenants.

In some implementations, the user systems 12 (which also can be clientsystems) communicate with the application servers 100 to request andupdate system-level and tenant-level data from the system 16. Suchrequests and updates can involve sending one or more queries to tenantdatabase 22 or system database 24. The system 16 (for example, anapplication server 100 in the system 16) can automatically generate oneor more SQL statements (for example, one or more SQL queries) designedto access the desired information. System database 24 can generate queryplans to access the requested data from the database. The term “queryplan” generally refers to one or more operations used to accessinformation in a database system.

Each database can generally be viewed as a collection of objects, suchas a set of logical tables, containing data fitted into predefined orcustomizable categories. A “table” is one representation of a dataobject, and may be used herein to simplify the conceptual description ofobjects and custom objects according to some implementations. It shouldbe understood that “table” and “object” may be used interchangeablyherein. Each table generally contains one or more data categorieslogically arranged as columns or fields in a viewable schema. Each rowor element of a table can contain an instance of data for each categorydefined by the fields. For example, a CRM database can include a tablethat describes a customer with fields for basic contact information suchas name, address, phone number, fax number, etc. Another table candescribe a purchase order, including fields for information such ascustomer, product, sale price, date, etc. In some MTS implementations,standard entity tables can be provided for use by all tenants. For CRMdatabase applications, such standard entities can include tables forcase, account, contact, lead, and opportunity data objects, eachcontaining pre-defined fields. As used herein, the term “entity” alsomay be used interchangeably with “object” and “table.”

In some MTS implementations, tenants are allowed to create and storecustom objects, or may be allowed to customize standard entities orobjects, for example by creating custom fields for standard objects,including custom index fields. Commonly assigned U.S. Pat. No.7,779,039, titled CUSTOM ENTITIES AND FIELDS IN A MULTI-TENANT DATABASESYSTEM, by Weissman et al., issued on Aug. 17, 2010, and herebyincorporated by reference in its entirety and for all purposes, teachessystems and methods for creating custom objects as well as customizingstandard objects in a multi-tenant database system. In someimplementations, for example, all custom entity data rows are stored ina single multi-tenant physical table, which may contain multiple logicaltables per organization. It is transparent to customers that theirmultiple “tables” are in fact stored in one large table or that theirdata may be stored in the same table as the data of other customers.

FIG. 2A shows a system diagram illustrating example architecturalcomponents of an on-demand database service environment 200 according tosome implementations. A client machine communicably connected with thecloud 204, generally referring to one or more networks in combination,as described herein, can communicate with the on-demand database serviceenvironment 200 via one or more edge routers 208 and 212. A clientmachine can be any of the examples of user systems 12 described above.The edge routers can communicate with one or more core switches 220 and224 through a firewall 216. The core switches can communicate with aload balancer 228, which can distribute server load over different pods,such as the pods 240 and 244. The pods 240 and 244, which can eachinclude one or more servers or other computing resources, can performdata processing and other operations used to provide on-demand services.Communication with the pods can be conducted via pod switches 232 and236. Components of the on-demand database service environment cancommunicate with database storage 256 through a database firewall 248and a database switch 252.

As shown in FIGS. 2A and 2B, accessing an on-demand database serviceenvironment can involve communications transmitted among a variety ofdifferent hardware or software components. Further, the on-demanddatabase service environment 200 is a simplified representation of anactual on-demand database service environment. For example, while onlyone or two devices of each type are shown in FIGS. 2A and 2B, someimplementations of an on-demand database service environment can includeanywhere from one to several devices of each type. Also, the on-demanddatabase service environment need not include each device shown in FIGS.2A and 2B, or can include additional devices not shown in FIGS. 2A and2B.

Additionally, it should be appreciated that one or more of the devicesin the on-demand database service environment 200 can be implemented onthe same physical device or on different hardware. Some devices can beimplemented using hardware or a combination of hardware and software.Thus, terms such as “data processing apparatus,” “machine,” “server” and“device” as used herein are not limited to a single hardware device,rather references to these terms can include any suitable combination ofhardware and software configured to provide the described functionality.

The cloud 204 is intended to refer to a data network or multiple datanetworks, often including the Internet. Client machines communicablyconnected with the cloud 204 can communicate with other components ofthe on-demand database service environment 200 to access servicesprovided by the on-demand database service environment. For example,client machines can access the on-demand database service environment toretrieve, store, edit, or process information. In some implementations,the edge routers 208 and 212 route packets between the cloud 204 andother components of the on-demand database service environment 200. Forexample, the edge routers 208 and 212 can employ the Border GatewayProtocol (BGP). The BGP is the core routing protocol of the Internet.The edge routers 208 and 212 can maintain a table of IP networks or‘prefixes’, which designate network reachability among autonomoussystems on the Internet.

In some implementations, the firewall 216 can protect the innercomponents of the on-demand database service environment 200 fromInternet traffic. The firewall 216 can block, permit, or deny access tothe inner components of the on-demand database service environment 200based upon a set of rules and other criteria. The firewall 216 can actas one or more of a packet filter, an application gateway, a statefulfilter, a proxy server, or any other type of firewall.

In some implementations, the core switches 220 and 224 are high-capacityswitches that transfer packets within the on-demand database serviceenvironment 200. The core switches 220 and 224 can be configured asnetwork bridges that quickly route data between different componentswithin the on-demand database service environment. In someimplementations, the use of two or more core switches 220 and 224 canprovide redundancy or reduced latency.

In some implementations, the pods 240 and 244 perform the core dataprocessing and service functions provided by the on-demand databaseservice environment. Each pod can include various types of hardware orsoftware computing resources. An example of the pod architecture isdiscussed in greater detail with reference to FIG. 2B. In someimplementations, communication between the pods 240 and 244 is conductedvia the pod switches 232 and 236. The pod switches 232 and 236 canfacilitate communication between the pods 240 and 244 and clientmachines communicably connected with the cloud 204, for example via coreswitches 220 and 224. Also, the pod switches 232 and 236 may facilitatecommunication between the pods 240 and 244 and the database storage 256.In some implementations, the load balancer 228 can distribute workloadbetween the pods 240 and 244. Balancing the on-demand service requestsbetween the pods can assist in improving the use of resources,increasing throughput, reducing response times, or reducing overhead.The load balancer 228 may include multilayer switches to analyze andforward traffic.

In some implementations, access to the database storage 256 is guardedby a database firewall 248. The database firewall 248 can act as acomputer application firewall operating at the database applicationlayer of a protocol stack. The database firewall 248 can protect thedatabase storage 256 from application attacks such as structure querylanguage (SQL) injection, database rootkits, and unauthorizedinformation disclosure. In some implementations, the database firewall248 includes a host using one or more forms of reverse proxy services toproxy traffic before passing it to a gateway router. The databasefirewall 248 can inspect the contents of database traffic and blockcertain content or database requests. The database firewall 248 can workon the SQL application level atop the TCP/IP stack, managingapplications' connection to the database or SQL management interfaces aswell as intercepting and enforcing packets traveling to or from adatabase network or application interface.

In some implementations, communication with the database storage 256 isconducted via the database switch 252. The multi-tenant database storage256 can include more than one hardware or software components forhandling database queries. Accordingly, the database switch 252 candirect database queries transmitted by other components of the on-demanddatabase service environment (for example, the pods 240 and 244) to thecorrect components within the database storage 256. In someimplementations, the database storage 256 is an on-demand databasesystem shared by many different organizations as described above withreference to FIGS. 1A and 1B.

FIG. 2B shows a system diagram further illustrating examplearchitectural components of an on-demand database service environmentaccording to some implementations. The pod 244 can be used to renderservices to a user of the on-demand database service environment 200. Insome implementations, each pod includes a variety of servers or othersystems. The pod 244 includes one or more content batch servers 264,content search servers 268, query servers 282, file force servers 286,access control system (ACS) servers 280, batch servers 284, and appservers 288. The pod 244 also can include database instances 290, quickfile systems (QFS) 292, and indexers 294. In some implementations, someor all communication between the servers in the pod 244 can betransmitted via the switch 236.

In some implementations, the app servers 288 include a hardware orsoftware framework dedicated to the execution of procedures (forexample, programs, routines, scripts) for supporting the construction ofapplications provided by the on-demand database service environment 200via the pod 244. In some implementations, the hardware or softwareframework of an app server 288 is configured to execute operations ofthe services described herein, including performance of the blocks ofvarious methods or processes described herein. In some alternativeimplementations, two or more app servers 288 can be included andcooperate to perform such methods, or one or more other serversdescribed herein can be configured to perform the disclosed methods.

The content batch servers 264 can handle requests internal to the pod.Some such requests can be long-running or not tied to a particularcustomer. For example, the content batch servers 264 can handle requestsrelated to log mining, cleanup work, and maintenance tasks. The contentsearch servers 268 can provide query and indexer functions. For example,the functions provided by the content search servers 268 can allow usersto search through content stored in the on-demand database serviceenvironment. The file servers 286 can manage requests for informationstored in the file storage 298. The file storage 298 can storeinformation such as documents, images, and basic large objects (BLOBs).By managing requests for information using the file force servers 286,the image footprint on the database can be reduced. The query servers282 can be used to retrieve information from one or more file systems.For example, the query system 282 can receive requests for informationfrom the app servers 288 and transmit information queries to the NFS 296located outside the pod.

The pod 244 can share a database instance 290 configured as amulti-tenant environment in which different organizations share accessto the same database. Additionally, services rendered by the pod 244 maycall upon various hardware or software resources. In someimplementations, the ACS servers 280 control access to data, hardwareresources, or software resources. In some implementations, the batchservers 284 process batch jobs, which are used to run tasks at specifiedtimes. For example, the batch servers 284 can transmit instructions toother servers, such as the app servers 288, to trigger the batch jobs.

In some implementations, a QFS 292 is an open source file systemavailable from Sun Microsystems® of Santa Clara, Calif. The QFS canserve as a rapid-access file system for storing and accessinginformation available within the pod 244. The QFS 292 can support somevolume management capabilities, allowing many disks to be groupedtogether into a file system. File system metadata can be kept on aseparate set of disks, which can be useful for streaming applicationswhere long disk seeks cannot be tolerated. Thus, the QFS system cancommunicate with one or more content search servers 268 or indexers 294to identify, retrieve, move, or update data stored in the network filesystems 296 or other storage systems.

In some implementations, one or more query servers 282 communicate withthe NFS 296 to retrieve or update information stored outside of the pod244. The NFS 296 can allow servers located in the pod 244 to accessinformation to access files over a network in a manner similar to howlocal storage is accessed. In some implementations, queries from thequery servers 282 are transmitted to the NFS 296 via the load balancer228, which can distribute resource requests over various resourcesavailable in the on-demand database service environment. The NFS 296also can communicate with the QFS 292 to update the information storedon the NFS 296 or to provide information to the QFS 292 for use byservers located within the pod 244.

In some implementations, the pod includes one or more database instances290. The database instance 290 can transmit information to the QFS 292.When information is transmitted to the QFS, it can be available for useby servers within the pod 244 without using an additional database call.In some implementations, database information is transmitted to theindexer 294. Indexer 294 can provide an index of information availablein the database 290 or QFS 292. The index information can be provided tofile force servers 286 or the QFS 292.

II. Enterprise Social Networking

As initially described above, in some implementations, some of themethods, processes, devices and systems described herein can implement,or be used in the context of, enterprise social networking. Some onlineenterprise social networks can be implemented in various settings,including businesses, organizations and other enterprises (all of whichare used interchangeably herein). For instance, an online enterprisesocial network can be implemented to connect users within a businesscorporation, partnership or organization, or a group of users withinsuch an enterprise. For instance, a Chatter® can be used by users whoare employees in a business organization to share data, communicate, andcollaborate with each other for various enterprise-related purposes.Some of the disclosed methods, processes, devices, systems andcomputer-readable storage media described herein can be configured ordesigned for use in a multi-tenant database environment, such asdescribed above with respect to system 16. In an example implementation,each organization or a group within the organization can be a respectivetenant of the system.

In some implementations, each user of the database system 16 isassociated with a “user profile.” A user profile refers generally to acollection of data about a given user. The data can include generalinformation, such as a name, a title, a phone number, a photo, abiographical summary, or a status (for example, text describing what theuser is currently doing, thinking or expressing). As described below,the data can include messages created by other users. In implementationsin which there are multiple tenants, a user is typically associated witha particular tenant (or “organization”). For example, a user could be asalesperson of an organization that is a tenant of the database system16.

A “group” generally refers to a collection of users within anorganization. In some implementations, a group can be defined as userswith the same or a similar attribute, or by membership or subscription.Groups can have various visibilities to users within an enterprisesocial network. For example, some groups can be private while others canbe public. In some implementations, to become a member within a privategroup, and to have the capability to publish and view feed items on thegroup's group feed, a user must request to be subscribed to the group(and be accepted by, for example, an administrator or owner of thegroup), be invited to subscribe to the group (and accept), or bedirectly subscribed to the group (for example, by an administrator orowner of the group). In some implementations, any user within theenterprise social network can subscribe to or follow a public group (andthus become a “member” of the public group) within the enterprise socialnetwork.

A “record” generally refers to a data entity, such as an instance of adata object created by a user or group of users of the database system16. Such records can include, for example, data objects representing andmaintaining data for accounts, cases, opportunities, leads, files,documents, orders, pricebooks, products, solutions, reports andforecasts, among other possibilities. For example, a record can be for abusiness partner or potential business partner (for example, a client,vendor, distributor, etc.) of a user or a user's organization, and caninclude information describing an entire enterprise, subsidiaries of anenterprise, or contacts at the enterprise. As another example, a recordcan be a project that a user or group of users is/are working on, suchas an opportunity (for example, a possible sale) with an existingpartner, or a project that the user is trying to obtain. A record hasdata fields that are defined by the structure of the object (forexample, fields of certain data types and purposes). A record also canhave custom fields defined by a user or organization. A field caninclude (or include a link to) another record, thereby providing aparent-child relationship between the records.

Records also can have various visibilities to users within an enterprisesocial network. For example, some records can be private while otherscan be public. In some implementations, to access a private record, andto have the capability to publish and view feed items on the record'srecord feed, a user must request to be subscribed to the record (and beaccepted by, for example, an administrator or owner of the record), beinvited to subscribe to the record (and accept), be directly subscribedto the record or be shared the record (for example, by an administratoror owner of the record). In some implementations, any user within theenterprise social network can subscribe to or follow a public recordwithin the enterprise social network.

In some online enterprise social networks, users also can follow oneanother by establishing “links” or “connections” with each other,sometimes referred to as “friending” one another. By establishing such alink, one user can see information generated by, generated about, orotherwise associated with another user. For instance, a first user cansee information posted by a second user to the second user's profilepage. In one example, when the first user is following the second user,the first user's news feed can receive a post from the second usersubmitted to the second user's profile feed.

In some implementations, users can access one or more enterprise networkfeeds (also referred to herein simply as “feeds”), which includepublications presented as feed items or entries in the feed. A networkfeed can be displayed in a graphical user interface (GUI) on a displaydevice such as the display of a user's computing device as describedabove. The publications can include various enterprise social networkinformation or data from various sources and can be stored in thedatabase system 16, for example, in tenant database 22. In someimplementations, feed items of information for or about a user can bepresented in a respective user feed, feed items of information for orabout a group can be presented in a respective group feed, and feeditems of information for or about a record can be presented in arespective record feed. A second user following a first user, a firstgroup, or a first record can automatically receive the feed itemsassociated with the first user, the first group or the first record fordisplay in the second user's news feed. In some implementations, a userfeed also can display feed items from the group feeds of the groups therespective user subscribes to, as well as feed items from the recordfeeds of the records the respective user subscribes to.

The term “feed item” (or feed element) refers to an item of information,which can be viewable in a feed. Feed items can include publicationssuch as messages (for example, user-generated textual posts orcomments), files (for example, documents, audio data, image data, videodata or other data), and “feed-tracked” updates associated with a user,a group or a record (feed-tracked updates are described in greaterdetail below). A feed item, and a feed in general, can includecombinations of messages, files and feed-tracked updates. Documents andother files can be included in, linked with, or attached to a post orcomment. For example, a post can include textual statements incombination with a document. The feed items can be organized inchronological order or another suitable or desirable order (which can becustomizable by a user) when the associated feed is displayed in agraphical user interface (GUI), for instance, on the user's computingdevice.

Messages such as posts can include alpha-numeric or othercharacter-based user inputs such as words, phrases, statements,questions, emotional expressions, or symbols. In some implementations, acomment can be made on any feed item. In some implementations, commentsare organized as a list explicitly tied to a particular feed item suchas a feed-tracked update, post, or status update. In someimplementations, comments may not be listed in the first layer (in ahierarchal sense) of feed items, but listed as a second layer branchingfrom a particular first layer feed item. In some implementations, a“like” or “dislike” also can be submitted in response to a particularpost, comment or other publication.

A “feed-tracked update,” also referred to herein as a “feed update,” isanother type of publication that may be presented as a feed item andgenerally refers to data representing an event. A feed-tracked updatecan include text generated by the database system in response to theevent, to be provided as one or more feed items for possible inclusionin one or more feeds. In one implementation, the data can initially bestored by the database system in, for example, tenant database 22, andsubsequently used by the database system to create text for describingthe event. Both the data and the text can be a feed-tracked update, asused herein. In some implementations, an event can be an update of arecord and can be triggered by a specific action by a user. Whichactions trigger an event can be configurable. Which events havefeed-tracked updates created and which feed updates are sent to whichusers also can be configurable. Messages and feed updates can be storedas a field or child object of a record. For example, the feed can bestored as a child object of the record.

As described above, a network feed can be specific to an individual userof an online social network. For instance, a user news feed (or “userfeed”) generally refers to an aggregation of feed items generated for aparticular user, and in some implementations, is viewable only to therespective user on a home page of the user. In some implementations auser profile feed (also referred to as a “user feed”) is another type ofuser feed that refers to an aggregation of feed items generated by orfor a particular user, and in some implementations, is viewable only bythe respective user and other users following the user on a profile pageof the user. As a more specific example, the feed items in a userprofile feed can include posts and comments that other users make aboutor send to the particular user, and status updates made by theparticular user. As another example, the feed items in a user profilefeed can include posts made by the particular user and feed-trackedupdates initiated based on actions of the particular user.

As is also described above, a network feed can be specific to a group ofenterprise users of an online enterprise social network. For instance, agroup news feed (or “group feed”) generally refers to an aggregation offeed items generated for or about a particular group of users of thedatabase system 16 and can be viewable by users following or subscribedto the group on a profile page of the group. For example, such feeditems can include posts made by members of the group or feed-trackedupdates about changes to the respective group (or changes to documentsor other files shared with the group). Members of the group can view andpost to a group feed in accordance with a permissions configuration forthe feed and the group. Publications in a group context can includedocuments, posts, or comments. In some implementations, the group feedalso includes publications and other feed items that are about the groupas a whole, the group's purpose, the group's description, a status ofthe group, and group records and other objects stored in associationwith the group. Threads of publications including updates and messages,such as posts, comments, likes, etc., can define conversations andchange over time. The following of a group allows a user to collaboratewith other users in the group, for example, on a record or on documentsor other files (which may be associated with a record).

As is also described above, a network feed can be specific to a recordin an online enterprise social network. For instance, a record news feed(or “record feed”) generally refers to an aggregation of feed itemsabout a particular record in the database system 16 and can be viewableby users subscribed to the record on a profile page of the record. Forexample, such feed items can include posts made by users about therecord or feed-tracked updates about changes to the respective record(or changes to documents or other files associated with the record).Subscribers to the record can view and post to a record feed inaccordance with a permissions configuration for the feed and the record.Publications in a record context also can include documents, posts, orcomments. In some implementations, the record feed also includespublications and other feed items that are about the record as a whole,the record's purpose, the record's description, and other records orother objects stored in association with the record. Threads ofpublications including updates and messages, such as posts, comments,likes, etc., can define conversations and change over time. Thefollowing of a record allows a user to track the progress of that recordand collaborate with other users subscribing to the record, for example,on the record or on documents or other files associated with the record.

In some implementations, data is stored in database system 16, includingtenant database 22, in the form of “entity objects” (also referred toherein simply as “entities”). In some implementations, entities arecategorized into “Records objects” and “Collaboration objects.” In somesuch implementations, the Records object includes all records in theenterprise social network. Each record can be considered a sub-object ofthe overarching Records object. In some implementations, Collaborationobjects include, for example, a “Users object,” a “Groups object,” a“Group-User relationship object,” a “Record-User relationship object”and a “Feed Items object.”

In some implementations, the Users object is a data structure that canbe represented or conceptualized as a “Users Table” that associatesusers to information about or pertaining to the respective usersincluding, for example, metadata about the users. In someimplementations, the Users Table includes all of the users within anorganization. In some other implementations, there can be a Users Tablefor each division, department, team or other sub-organization within anorganization. In implementations in which the organization is a tenantof a multi-tenant enterprise social network platform, the Users Tablecan include all of the users within all of the organizations that aretenants of the multi-tenant enterprise social network platform. In someimplementations, each user can be identified by a user identifier(“UserID”) that is unique at least within the user's respectiveorganization. In some such implementations, each organization also has aunique organization identifier (“OrgID”).

In some implementations, the Groups object is a data structure that canbe represented or conceptualized as a “Groups Table” that associatesgroups to information about or pertaining to the respective groupsincluding, for example, metadata about the groups. In someimplementations, the Groups Table includes all of the groups within theorganization. In some other implementations, there can be a Groups Tablefor each division, department, team or other sub-organization within anorganization. In implementations in which the organization is a tenantof a multi-tenant enterprise social network platform, the Groups Tablecan include all of the groups within all of the organizations that aretenants of the multitenant enterprise social network platform. In someimplementations, each group can be identified by a group identifier(“GroupID”) that is unique at least within the respective organization.

In some implementations, the database system 16 includes a “Group-Userrelationship object.” The Group-User relationship object is a datastructure that can be represented or conceptualized as a “Group-UserTable” that associates groups to users subscribed to the respectivegroups. In some implementations, the Group-User Table includes all ofthe groups within the organization. In some other implementations, therecan be a Group-User Table for each division, department, team or othersub-organization within an organization. In implementations in which theorganization is a tenant of a multi-tenant enterprise social networkplatform, the Group-User Table can include all of the groups within allof the organizations that are tenants of the multitenant enterprisesocial network platform.

In some implementations, the Records object is a data structure that canbe represented or conceptualized as a “Records Table” that associatesrecords to information about or pertaining to the respective recordsincluding, for example, metadata about the records. In someimplementations, the Records Table includes all of the records withinthe organization. In some other implementations, there can be a RecordsTable for each division, department, team or other sub-organizationwithin an organization. In implementations in which the organization isa tenant of a multi-tenant enterprise social network platform, theRecords Table can include all of the records within all of theorganizations that are tenants of the multitenant enterprise socialnetwork platform. In some implementations, each record can be identifiedby a record identifier (“RecordID”) that is unique at least within therespective organization.

In some implementations, the database system 16 includes a “Record-Userrelationship object.” The Record-User relationship object is a datastructure that can be represented or conceptualized as a “Record-UserTable” that associates records to users subscribed to the respectiverecords. In some implementations, the Record-User Table includes all ofthe records within the organization. In some other implementations,there can be a Record-User Table for each division, department, team orother sub-organization within an organization. In implementations inwhich the organization is a tenant of a multi-tenant enterprise socialnetwork platform, the Record-User Table can include all of the recordswithin all of the organizations that are tenants of the multitenantenterprise social network platform.

In some implementations, the database system 16 includes a “Feed Itemsobject.” The Feed items object is a data structure that can berepresented or conceptualized as a “Feed Items Table” that associatesusers, records and groups to posts, comments, documents or otherpublications to be displayed as feed items in the respective user feeds,record feeds and group feeds, respectively. In some implementations, theFeed Items Table includes all of the feed items within the organization.In some other implementations, there can be a Feed Items Table for eachdivision, department, team or other sub-organization within anorganization. In implementations in which the organization is a tenantof a multi-tenant enterprise social network platform, the Feed ItemsTable can include all of the feed items within all of the organizationsthat are tenants of the multitenant enterprise social network platform.

Enterprise social network news feeds are different from typicalconsumer-facing social network news feeds (for example, FACEBOOK®) inmany ways, including in the way they prioritize information. Inconsumer-facing social networks, the focus is generally on helping thesocial network users find information that they are personallyinterested in. But in enterprise social networks, it can, in someinstances, applications, or implementations, be desirable from anenterprise's perspective to only distribute relevant enterprise-relatedinformation to users and to limit the distribution of irrelevantinformation. In some implementations, relevant enterprise-relatedinformation refers to information that would be predicted or expected tobenefit the enterprise by virtue of the recipients knowing theinformation, such as an update to a database record maintained by or onbehalf of the enterprise. Thus, the meaning of relevance differssignificantly in the context of a consumer-facing social network ascompared with an employee-facing or organization member-facingenterprise social network.

In some implementations, when data such as posts or comments from one ormore enterprise users are submitted to a network feed for a particularuser, group, record or other object within an online enterprise socialnetwork, an email notification or other type of network communicationmay be transmitted to all users following the respective user, group,record or object in addition to the inclusion of the data as a feed itemin one or more user, group, record or other feeds. In some onlineenterprise social networks, the occurrence of such a notification islimited to the first instance of a published input, which may form partof a larger conversation. For instance, a notification may betransmitted for an initial post, but not for comments on the post. Insome other implementations, a separate notification is transmitted foreach such publication, such as a comment on a post.

FIG. 3 shows an example of a group feed on a group profile pageaccording to some implementations. As shown, a feed item 310 shows thata user has posted a document to the group feed. The text “Bill Bauer hasposted the document Competitive Insights” can be generated by thedatabase system in a similar manner as feed-tracked updates about arecord being changed. A feed item 320 shows a post to the group, alongwith comments 330 from Ella Johnson, James Saxon, Mary Moore and BillBauer.

FIG. 4 shows an example of a record feed on a record profile pagedisplay according to some implementations. The record feed includes afeed-tracked update, a post, and comments. Feed item 410 shows afeed-tracked update based on the event of submitting a discount forapproval. A feed-tracked update may be generated by the systemautomatically, as noted. Other feed items show posts, for example, fromBill Bauer, made to the record and comments, for example, from Erica Lawand Jake Rapp, made on the posts. Adjacent to each post, there arebuttons or controls to download the corresponding ppt file, and also abutton marked “Sync” further described shortly.

III. Collaboration Among Multiple Users

One feature of the present disclosure is to enable collaboration amongmultiple users on the creation and revisions to any type of digitalelectronic file. In one embodiment, the users may be members of a group.FIG. 5 shows an example of a group feed screen display. Here, the Admin“Pola” of a private group called “Sync Client” posted a request formembers to post presentations for a demonstration. Members John Goldie,Robert Lee, James Johnson and Richard Lee have posted replies orcomments on the feed, as shown in the illustration. Each of them hasposted a file as requested, specifically .ppt files in thisillustration, although any other file types may be used.

Adjacent to each post are buttons or controls to download thecorresponding attached file (“Download ppt”) or to “Sync” the file. Inthe latter case, the button requests synchronization of the file. Thisrequest (1) causes download of the selected file from the cloud databaseto the requesting user's local file system; and (2) subscribes theuser's machine(s) to automatically receive updates to the downloadedfile. Accordingly, any time the file is changed, by the original authoror by another authorized user, the local file system copy will beupdated or replaced to match the latest version. In the former case(“Download ppt”), a simple download of the file to the local file systemleaves it “orphaned” such that any subsequent updates or changes must bemade by the user manually, and they are not communicated to othermembers of the group unless the local user sends out the changes“manually” by posting a message or the like.

A pop-up, pull-down post menu, or similar user interface component 500may be provided on the feed display. It may provide for variousoperations such as bookmarking or adding a new topic. One option thatmay appear, in the case that a suitable synchronization clientapplication is running on the user's local machine—further describedbelow—is a “Sync all files” button. Clicking or otherwise selecting thisoption will trigger synchronization of all the files posted in the feedfrom the current time forward. Preferably, this action will causeautomatic download of the latest versions of all the posted filescurrently in the feed, to a selected folder in the each user's localfile system, and it will subscribe each user to automatically receiveall updates to that set of files as further explained below. The updatesor changes automatically received will include those generated by theposting author, as well as those generated by any or all otherauthorized group members who are subscribed for synchronization of thecorresponding file. Further, all new files subsequently posted to thefeed will also be synced, i.e., automatically downloaded to all membersof the group who subscribed to synchronization (for example, with the“Sync all files” button). In this way, team members can collaborate oncreating and or editing one or more files, and each of their localcopies of the file(s) will remain automatically synchronized with thelatest version of the file. Put another way, the user is subscribed tosync with the entire feed, and not just to selected files.

In some embodiments, clicking the “Synchronize all files” operation mayopen a directory in which a target folder may be created or selected.The synced files will be copied there. Various permissions may be usedto control changes to a file, while enabling collaboration. For example,if one user is a “Viewer” for the file, the file may be downloaded totheir machine(s) with read-only (RO) permissions. If a user hasCollaborator rights on the file, the file may be downloaded with ReadWrite permissions to that user. Thereafter, if the owner or anyauthorized “Collaborator” makes any new revision to the file, it will beupdated in the cloud, and it will be automatically downloaded to allusers who are subscribed for synchronization of that file. Morespecifically, revisions are not typically made “in the cloud” directly.In some embodiments, revisions may be made in a user's local machine,and a synchronize application program executed on the local machine mayupload the changes or revised file to the cloud as further explainedbelow. If a user has multiple machines, a synchronize applicationprogram may automatically sync the files all over of the user'smachines.

FIG. 6 shows an example of a local file system directory in whichselected files may be automatically collected and maintained insynchrony. In this illustration, a folder called “Salesforce Files” isused by a local synchronization client application for local filestorage. A subfolder named Presentations (or any other valid name) iscreated by the local machine user, and designated as a target directoryfor storing files to be synchronized. For example, a user may designatea different folder for each group or feed in which they are subscribedfor synchronize of at least one file. The folder names are merely forillustration and are not critical. In the figure, the four .pptpresentation files that were posted in the feed in FIG. 5 are shown asstored in the local directory. In an embodiment, download of the fourfiles was accomplished by a single click of the “Sync all files” buttondescribed above with regard to FIG. 5. These local copies will beautomatically updated to reflect the latest version of each file(synchronized) as long as they are subscribed for synchronization.

FIG. 7 is a simplified block diagram illustrating an example of a systemarchitecture that employs a client application program in support ofsynchronization of database files for collaboration. In FIG. 7, a cloudsystem indicated by dashed line 700 may be similar to the cloud systemdescribed above with regard to FIGS. 1-3. The cloud system 700 mayinclude one or more application servers 702 which may be configured toprovide various services, and run applications, for users, cliententities or tenants. In an embodiment, application servers 702 may becoupled to one or more database systems 706. The app server 702 mayupload a file from a user machine (not shown) through a web applicationor other system or protocol, indicated at file upload 708. For example,a file may be uploaded to a feed. The uploaded file may be stored in thedatabase 706 by the application server.

Events that affect a file, such as file uploads, file changes, etc. maybe communicated by the app server to a notification server 710. Aprimary function of the notification server is to send or publishnotifications of such events to appropriate client devices, illustratedat path 730. In an embodiment, the client devices may be identified asdevices associated with a user who has subscribed to receive updates,i.e., remain synchronized, with regard to one or more particular filesstored in the system. Where a file is associated to a group or otherentity, the notification server may send notification of changes to thefile to the associated group.

In a preferred embodiment, notifications may be sent from thenotification server 710 to one or more synchronization clientapplications (“client app” or “sync app”) 714. The client application714 may be executed on a user machine, such as a user system 12 shown inprevious drawings. The user systems 12 can be implemented as anycomputing device(s) or other data processing apparatus or systems usableby users to access the cloud system. For example, any of user systems 12can be a desktop computer, a work station, a laptop computer, a tabletcomputer, a handheld computing device, a mobile cellular phone (forexample, a “smartphone”), or any other Wi-Fi-enabled device, wirelessaccess protocol (WAP)-enabled device, or other computing device capableof interfacing directly or indirectly to the Internet or other network.A user may be associated with more than one device or machine. TheNotification Server may be configured to send notifications of fileevents to all of a user's associated devices that are running a clientapp such as 714. In some embodiments, the client application maymaintain a persistent connection with the cloud system. It may checkperiodically for notifications from the notification server 710. Inother embodiments, various push or pull notifications may be used.

The client app 714 may be authenticated by an authentication server 720.The client app is configured to receive notifications of file additionsor changes via path 730 using any appropriate format or protocol nowknown or later developed. The application server 702 may manage transferof files between the cloud system and the client app 714, as indicatedby pathway or channel 736. Such file transfers may be implemented withone or more intermediary entities or services (not shown). In someembodiments, the client app may request a file from the applicationserver.

FIG. 8 is a simplified block diagram showing the principle components ofone example of a synchronization client application program. The clientapp (for example, 714 in FIG. 7), is communicatively coupled to thecloud 700. Preferably, this connection may be a persistent or “alwayson” connection. This connection may be established with an applicationserver (702 in FIG. 7). A notification engine 802 is configured toreceive notifications of events from the cloud 700 when a file is addedor changed. That is, the events affect the “cloud copy” or version of afile. The notification engine 802 passes information about the cloudcopy file change to a journaling system 804. Such events may include,for example, a file download, update, rename, etc. In the cloud databasesystem. In an embodiment, the journaling systems keeps track of allchanges to the files. It may maintain a journal for that purpose, whichmay be stored in a database 806 operatively coupled to the journalingsystem 804. (Database 806 in the client app is distinct from thedatabase 706 in the cloud.)

In addition, local components should be provided to monitor and tracklocal changes to a file that has been marked or selected forsynchronization. To that end, a file is stored in a local file system.For example, a Windows or Mac file system 814 may be provisioned on auser machine. A file system watcher component 810 is configured tomonitor the file system 814. In an embodiment, the FS watcher copies thefile to the database 806, and then updates the file (in the database)responsive to changes observed in the local file system 814. Inaddition, the FS watcher component notifies the Journaling System 804 oflocal changes to the file, indicated via path 812. Thus, in a preferredembodiment, the journaling system keeps track of both cloud and localchanges to the files, and records the changes in the journal in database806.

A synchronization engine component 810 may be operatively coupled to thedatabase 806. In an embodiment, the synchronization engine monitorsevents stored in the journal, and it also obtains the latest fileinformation from the cloud. The synchronize engine 810 may communicatewith the cloud as needed (on demand), for example, when a journal entryindicates a change to a file. The sync engine 810 may communicate withthe application server. In an embodiment, the synchronize engine “knows”the affected file ID, filename, etc. Logic implemented in thesynchronize engine compares the latest cloud metadata to thecorresponding file local metadata. Based on these inputs, thesynchronize engine determines an appropriate task to keep the filesynchronized to the latest version. Such a task may comprise, forexample, a file upload, in the case that the local version of the fileis more current (i.e., more recently changed), or a download from thecloud in the case that the cloud version is more current. Thesynchronize engine 810 may forward the determined task to a task engine820 to carry out the task. For example, a download from the cloud. In anembodiment, a streaming process 840 may be implemented for downloading afile from the cloud; it may inform the task engine when the download iscompleted.

A communication component or layer 860 may be provided in, or coupled tothe client application. For example, the communication component 860 mayimplement HTTPS, TCP, SSL or any other suitable data communicationprotocol, now known or later developed. The communication component maybe configured to communicate with an app server in the cloud, forexample, server 702 in FIG. 7, to upload or download a file as directedby the task engine. Responsive to completing a download operation, thetask engine may request the FS Watcher to copy the file to a designatedfolder in the local file system. An example is shown for illustration asthe “Salesforce Files” folder in FIG. 6. In the example, a subfoldernamed “Presentations” is designated to store a set of filescorresponding to the user group that is using them, for example, thegroup shown in the feed page in FIG. 5.

The client app 714 may include a user interface (UI) component 880. TheUI in one example may display a synchronize icon on the user's screendisplay, for example, at the top or title bar as shown in FIG. 9. Theimage in FIG. 9 shows the interface in use (for example, it may dropdown responsive to a pointer hovering), and it presents options such asopen the app file folder (in the image called Salesforce Files folder),etc. FIG. 10 illustrates a display of a file system folder of filesassociated with synchronization client application program. This foldermay be opened in response to the drop down control. In an embodiment,the client app begins synchronization automatically as soon as it islaunched. Synchronization activity may be indicated by some animation inthe app icon (here a cloud). The UI interface may indicate whether theclient app is currently syncing. It FIG. 9 it indicates that is itcurrently syncing, and further indicates its progress, “10 Files Left”in the illustration. If the user clicks “open [folder name]” (the nameis Salesforce Files in the example), the file system shows a list of thefiles being synchronized—as illustrated in FIG. 10, listing files 2.txtto 10.txt. In an embodiment, the interface may further display specificstatus for each file being syncing, as illustrated in the display panelshown in FIG. 11. Here, three files are still syncing and their names(2.txt, 10.txt etc.) are shown, along with current status (“Syncing”).In this way, the user interface provides convenient access to observewhat files are synced synced and their status.

Each of the members of a group of users who would collaborate on a filemay install an instance of the synchronization client applicationprogram on their machine, or on each one of their multiple machines ifthey choose to do so. One example of such a group is the groupassociated to the feed display example of FIG. 5. With a singleinstruction or “click” by the group admin (or other duly authorizeduser), all of the files in the feed will be synchronized to all of themembers of the group who run such a sync client. Any and all changesmade by an authorized collaborator thereafter will be automaticallydistributed to the local file systems on each of those user machinesthat have the sync client. Further, any new file added to the same feedwill be automatically distributed to all members of the feed who havethe sync client app. If a user machine is off-line or disconnected fromthe cloud for a time, or the sync client app is not running for a time,the app will “catch up” and sync the affected files to the latestversion automatically when it is again running and has connectivity. Ifthe app is running and cannot communicate with the cloud, it can queueup necessary actions, for example, using the task engine andcommunication interface components described above.

A user of the sync client application need not necessarily receive everyupdate to every synced file if they choose not to do so. For example, anunsync option or a pause sync per file option may be implemented. At thecloud level, a group admin, for example, may choose to pause or stopsyncing one or more of the files in the group feed. In an embodiment,the notification server may then stop sending notifications of eventsrelated to the selected file(s). At the client application level, a useralso may have an option to pause or stop syncing on a per file basis.These options may be added to the user interface described above. In anembodiment, the journaling system may then ignore, or treat differently,the selected file(s). In one example, an Unsync option may beimplemented so that it deletes the corresponding file locally butphysical the file still remains in the cloud. In another example, aPause sync function may retain the local file unchanged, except forlocal changes, but then sync it to the latest version in the cloud wheninstructed to resume syncing.

The specific details of the specific aspects of implementationsdisclosed herein may be combined in any suitable manner withoutdeparting from the spirit and scope of the disclosed implementations.However, other implementations may be directed to specificimplementations relating to each individual aspect, or specificcombinations of these individual aspects. Additionally, while thedisclosed examples are often described herein with reference to animplementation in which an on-demand database service environment isimplemented in a system having an application server providing a frontend for an on-demand database service capable of supporting multipletenants, the present implementations are not limited to multi-tenantdatabases or deployment on application servers Implementations may bepracticed using other database architectures, i.e., ORACLE®, DB2® by IBMand the like without departing from the scope of the implementationsclaimed.

It should also be understood that some of the disclosed implementationscan be embodied in the form of various types of hardware, software,firmware, or combinations thereof, including in the form of controllogic, and using such hardware or software in a modular or integratedmanner. Other ways or methods are possible using hardware and acombination of hardware and software. Additionally, any of the softwarecomponents or functions described in this application can be implementedas software code to be executed by one or more processors using anysuitable computer language such as, for example, Java, C++ or Perlusing, for example, existing or object-oriented techniques. The softwarecode can be stored as a computer- or processor-executable instructionsor commands on a physical non-transitory computer-readable medium.Examples of suitable media include random access memory (RAM), read onlymemory (ROM), magnetic media such as a hard-drive or a floppy disk, oran optical medium such as a compact disk (CD) or DVD (digital versatiledisk), flash memory, and the like, or any combination of such storage ortransmission devices. Computer-readable media encoded with thesoftware/program code may be packaged with a compatible device orprovided separately from other devices (for example, via Internetdownload). Any such computer-readable medium may reside on or within asingle computing device or an entire computer system, and may be amongother computer-readable media within a system or network. A computersystem, or other computing device, may include a monitor, printer, orother suitable display for providing any of the results mentioned hereinto a user.

While some implementations have been described herein, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of the present applicationshould not be limited by any of the implementations described herein,but should be defined only in accordance with the following andlater-submitted claims and their equivalents.

1. A method for a database system to support collaboration among usersof a file in a feed system of a multi-user social network provided bythe database system, the feed system managing and electronicallypublishing at least one feed comprising a series of feed items, the feedaccessible to a set of users associated with the feed for communicatingamong the set of users, wherein at least some of the users are permittedto upload a file to the feed from a remote computing device, the methodcomprising the steps of: establishing at the database system aconnection with a remote computing device; receiving at the databasesystem a request from the remote computing device to synchronize allfiles in a selected feed; at the database system, responsive to therequest, identifying a set of at least one file associated to theselected feed; at the database system, identifying a latest version ofeach file in the set; and automatically downloading the latest versionof each file in the set to the remote computing device.
 2. The method ofclaim 1 further comprising: identifying all users who aresynchronization subscribers to at least one of the set of files; andautomatically downloading the latest version of each file to which auser is a synchronization subscriber, to a machine associated with thecorresponding user.
 3. The method of claim 2 wherein the automaticdownloading step includes identifying at least one machine associated toeach synchronization subscriber and downloading the latest version ofthe file to all of the identified machines.
 4. The method of claim 1wherein the selected feed is associated with one of a group of CRMobjects, the group comprising an account, a contact, and an opportunity.5. The method of claim 1 further comprising associating a selected localfile folder in the remote computing device to the selected feed, anddownloading the latest version of each file in the set to the associatedlocal file folder.
 6. The method of claim 1 wherein: the database systemincludes at least one application server; the connection with a remotecomputing device is established with the application server; the requestfrom the remote computing device is received at the application server;responsive to the request, the application server identifies the set ofat least one file; the application server identifies the latest versionof each file in the set; and the application server causes thedownloading of the latest version of each file in the set to the remotecomputing device.
 7. The method of claim 6 and further comprising:identifying all users who are synchronization subscribers to at leastone of the set of files; and automatically downloading the latestversion of each file to which a user is a synchronization subscriber, tothe corresponding user.
 8. The method of claim 6 wherein the selectedfeed is associated with one of a group of CRM objects, the groupcomprising an account, a contact, and an opportunity.
 9. The method ofclaim 6 further comprising: monitoring the remote computing device todetect a modification of one of the files in the selected feed;responsive to detecting a modification of the file, uploading themodified file to the database system as the latest version of themodified file; and downloading the latest version of the modified filefrom the database system to each user who previously subscribed tosynchronization of the file.
 10. The method of claim 9 wherein:downloading the latest version of the modified file includes identifyingat least one machine associated to each synchronization subscriber anddownloading the latest version of the file to all of the identifiedmachines. downloading the latest version of the file to each one of theidentified machines associated to each synchronization subscriber.
 11. Acloud computing system comprising: a database system arranged to supportcollaboration among users of a file in a feed system of a multi-usersocial network provided by the database system, the feed system managingand electronically publishing at least one feed comprising a series offeed items, the feed accessible to a set of users associated with thefeed for communicating among the set of users, wherein at least some ofthe users are permitted to upload a file to the feed from a remotecomputing device; the database system including at least one applicationserver arranged to provide services, and run applications, for users orclient entities of the database system, wherein the application serveris configured to communicate selected events to the notification serverintroduced below, the events selected as those affecting a particularfile among a selected set of files uploaded to the feed; and thedatabase system including a notification server configured to receivethe selected events from the application server and to publishnotifications of the selected events to remote client devices; whereinthe published notifications are arranged to be used by the remote clientdevices to trigger synchronization of a corresponding local copy of theparticular file on each client device to a cloud copy of the particularfile maintained in the database system.
 12. The system of claim 11wherein the notification server is implemented as a software component.13. The system of claim 11 wherein the selected events include uploadinga new file to the feed and modifying an existing file in the feed, so asto enable the remote client devices to maintain synchronization bydownloading the new file or modifying a local copy of the modified file,as applicable, responsive to receiving a notification of the selectedevent.
 14. The system of claim 11 wherein the selected events includedeleting or renaming a file in the feed, so as to enable the remoteclient devices to maintain synchronization by deleting or renaming alocal copy of the affected file, as applicable, responsive to receivinga notification of the selected event.
 15. The system of claim 11 whereinthe feed is associated with one of a group of CRM objects, the groupcomprising an account, a contact, and an opportunity.
 16. The system ofclaim 11 wherein: the database system is configured to maintain a recordof users who are subscribed for synchronization of a particular file;and the notification server is configured to publish notifications ofthe selected events to the users who are subscribed for synchronizationof the particular file.
 17. A method comprising: at a user machine,establishing a connection with a cloud computing system that implementsa feed system of a multi-user social network, the feed system managingand electronically publishing at least one feed comprising a series offeed items, the feed accessible to a set of users associated with thefeed for communicating among the set of users, wherein at least some ofthe users are permitted to upload a file to the feed from a remotecomputing device; via the connection, receiving a notification of anevent from the cloud computing system, wherein the event affects aselected file associated to the feed; at the user machine, maintaining ajournal of the notifications received from the cloud computing system ofevents that affect a cloud copy of the selected file; at the usermachine, monitoring a local file system to detect changes that affect alocal copy of the selected file; at the user machine, adding to thejournal indicia of the detected changes to the local copy; at the usermachine, based at least in part on the journal entries, determining atask to synchronize the local copy and the cloud copy of the selectedfile; and at the user machine, executing the task to sync to synchronizethe local copy and the cloud copy of the selected file to a mostrecently changed version of the file, wherein executing the taskincludes communicating with the cloud computing system.
 18. The methodof claim 17 wherein determining the task includes obtaining metadataabout the cloud copy of the selected file from the cloud computingsystem, and comparing the obtained metadata to metadata generated bysaid monitoring of the local file system to detect changes that affectthe local copy of the selected file, to determine which is the mostrecently changed version of the file.
 19. The method of claim 17 whereinexecuting the task includes one of uploading the local copy of theselected file to the cloud computing system and downloading the cloudcopy of the selected file to the local file system.
 20. The method ofclaim 17 wherein executing the task to sync to synchronize the localcopy includes communicating with an application server of the cloudcomputing system.